-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds functionality for patch-based configuration #839
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## vara-dev #839 +/- ##
============================================
+ Coverage 68.30% 68.34% +0.04%
============================================
Files 333 334 +1
Lines 25762 25856 +94
============================================
+ Hits 17597 17672 +75
- Misses 8165 8184 +19
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, except for the mypy error. I'm not sure how to type this correctly.
Thing is, you cannot type-hint lambdas. One solution would be to make it a function instead (which is a bit overkill imo). |
Compile-time configurable projects can now be configured using patches.
Therefore, patches can specify a list of
feature_tags
.Case studies can contain a configuration map with
PatchConfiguration
s that contains a mapping from config id to a list of feature tags associated with this configuration.Configuration patches are selected by matching their feature tags to the feature tags of the given configuration.
Since there are multiple types of configuration maps now, their type must be specified using the key
config_type
in case study files.